Fix pipe historical extraction when device metadata is unavailable - #18541
Merged
jt2594838 merged 1 commit intoAug 31, 2026
Merged
Conversation
jt2594838
approved these changes
Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When a historical TsFile's
.resourcefile is missing or unreadable,TsFileResource.getDevices()can throw aRuntimeException. The historical pipe source only caughtIOException, so the file was skipped and the pipe could remain blocked waiting for historical extraction to complete.Solution
Treat runtime failures while reading device metadata the same as I/O failures: log the error and continue extracting the TsFile because it may match the configured pattern.
Tests
PipeHistoricalDataRegionTsFileAndDeletionSourceTest: 20 tests passed..tsfile.resourcewithFileTimeIndex.